NDIS Driver Notes v3.07 General NDIS Driver Notes for Intel's EtherExpress(TM) PRO/10 ISA LAN Adapter ===================================================================== Location of Driver: \NDIS\EPRO.DOS \NDIS\EPRO.OS2 Support files: \NDIS\EPROEDOS.NIF \NDIS\EPROEOS2.NIF \NDIS\PROTOCOL.INI \NDIS\OEMSETUP.INF \NDIS\MSLANMAN.BAT \NDIS\STNDNIF\EPRODOS.NIF \NDIS\STNDNIF\EPROOS2.NIF Sample Configuration Files -------------------------- CONFIG.SYS (for DOS will contain) DEVICE=C:\path\PROTMAN.DOS /I:C:\path DEVICE=C:\path\EPRO.DOS CONFIG.SYS (for OS/2 will contain) DEVICE=C:\path\PROTMAN.OS2 /I:C:\path DEVICE=C:\path\EPRO.OS2 PROTOCOL.INI (contains) [EPRO_NIF] DriverName=EPRO$ IOADDRESS=0x300 General Notes ------------- 1. If you have a Plug and Play BIOS and are running OS/2* or a NetWare* server, make sure you DISABLE Plug and Play on your adapter using SoftSet2 (Advanced Options menu). These environments don't support Plug and Play. If Plug and Play is enabled in these environments, the operating system may not be able to find your adapter. 2. Many different network operating systems use a standard 2.0.1 version NDIS driver to talk to the network adapter. The EtherExpress(TM) PRO/10 ISA adapter's NDIS driver conforms to Microsoft's 2.0.1 NDIS specification. 3. The EtherExpress PRO/10 ISA adapter disk contains the files you need to install and use the adapter card with a variety of NDIS-based operating systems. See details below to find out which subdirectory has the files you require. File Purpose ---- ------- EPRO.DOS: NDIS driver for DOS workstations. EPRO.OS2: NDIS driver for servers & OS/2 workstations. EPRODOS.NIF: The standard DOS NIF file used with Microsoft LAN Manager* installations. Other Network Operating systems may use this file during their installation. If so, copy the EPRO.DOS and this NIF file into the same directory and reference that directory. EPROOS2.NIF: The standard OS/2 NIF file used with Microsoft LAN Manager installations. Other Network Operating systems may use this file during their installation. If so, copy the EPRO.DOS and this NIF file into the same directory and reference that directory. EPROEDOS.NIF: An extended NIF file referenced by IBM LAN Support Program. Specify the \NDIS directory when installing so the installation procedure will find the correct NIF file. EPROEOS2.NIF: An extended NIF file referenced by IBM LAN Support Program. Specify the \NDIS directory when installing so the installation procedure will find the correct NIF file. PROTOCOL.INI: Fragment of the general PROTOCOL.INI file. This fragment contains information specific to the EtherExpress PRO/10 ISA adapter. Most installation procedures create this file for you. This file is provided as an example of what the EtherExpress PRO/10 ISA adapter section could look like. OEMSETUP.INF: The version located in the \NDIS subdirectory on the driver disk is used by IBM's LAN requester for DOS version 4.0 and Microsoft's Windows for Workgroups v3.10 installation. MSLANMAN.BAT: Executing this file creates the directory structure required for a Microsoft LAN Manager installation. Other NDIS installations may also look for this structure: \MSLANMAN.DOS\DRIVERS\ETHERNET\EPRO\EPRO.DOS (DOS) or \MSLANMAN.OS2\DRIVERS\ETHERNET\EPRO\EPRO.OS2 (OS/2) Hints and Tips -------------- 1. Parameters for the PROTOCOL.INI file are listed below. DRIVERNAME: (required) If you have a single adapter, use the syntax in the Sample Configuration file section. If you are installing multiple adapters, each adapter must have a unique driver name. Additional instances of the driver would be referenced by DRIVERNAME=EPROx$, where "x" would be a unique number 2 through 9. IOADDRESS: (optional for single adapter systems - except when set to certain addresses noted below) This value must match the adapter's I/O address. If the driver does not find the adapter at the specified I/O address, it will scan most of the I/O addresses that the adapter could be at and will load if it finds the adapter. The only addresses the driver doesn't scan are 2E0, 2F0 or 370. If you have used one of these address, this parameter isn't optional. If you use multiple adapters in one machine, make sure you specify the correct IOADDRESS for each board. Otherwise, the driver will fail when loading on the second card. INTERRUPT: (optional)(Syntax: INTERRUPT=5) This value specifies at load time a new interrupt that the adapter will use. The driver includes no check on the validity of this interrupt in the system, and therefore could easily be placed in conflict with another device and fail. If this feature is used, and the computer is warm booted, this interrupt will be programmed into the EEprom when the driver loads. NODE: (optional) This value sets the adapter's Individual Address, overriding the value read from the adapter EEprom. The address must consist of 12 hexadecimal digits, enclosed in double quotes. The value can not be all zeros. The value can not have the Multicast bit set. So, use only the hexadecimal digits 2, 6, A, or E as the second digit of the twelve required in the NODE ADDRESS parameter. Use any hexadecimal digits in all other positions. [Example: NODE = "02AA00123456"] 2. Plug and Play error message when loading the driver The PRO/10 adapter is a Plug and Play adapter, and if the adapter detects a Plug and Play BIOS in your computer, it will rely on that BIOS to configure it. Various BIOS setup configurations can cause the adapter not to be configured. Follow the suggestions listed in the message to fix the problem. Since BIOS differ in options, some BIOS may not allow you to adjust all the listed selections. Message: Your computer's Plug and Play BIOS couldn't configure your EtherExpress PRO/10 LAN Adapter. The probable cause is that your computer's BIOS isn't properly configured for this Plug and Play adapter. To keep the Plug and Play feature on the adapter, check the following: - Make sure your computer's BIOS has enough Interrupts (IRQs) designated for Plug and Play devices. - Check your computer's BIOS for a Plug and Play Activation level. Make sure it is set to configure Plug and Play devices. - Your computer may require a Plug and Play Configuration Manager. Check with your computer vendor for details. Or - Disable Plug and Play on this adapter by running SoftSet2. * Third-party trademarks are the property of their respective owners.